Quick-logon for computing device

ABSTRACT

Methods and systems for verifying a user&#39;s identity on a computing device using two-factor authentication are described. More particularly, the system can use a personal identification number input by a user, together with one or more of a secure browsing feature, a device fingerprint, and a token generator to authenticate the user on the computer.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/355,099, filed Mar. 15, 2019, entitled “Quick-Logon For Computing Device,” now allowed, which is a continuation of U.S. patent application Ser. No. 15/442,826, filed Feb. 27, 2017, entitled “Quick-Logon For Computing Device,” issued as U.S. Pat. No. 10,282,531 on May 7, 2019, which is a continuation-in-part of U.S. patent application Ser. No. 14/992,796, filed Jan. 11, 2016, entitled “Quick-Logon for Computing Device,” issued as U.S. Pat. No. 9,917,825 on Mar. 13, 2018, which is a continuation of U.S. patent application Ser. No. 14/301,856, filed Jun. 11, 2014, issued as U.S. Pat. No. 9,237,146 on Jan. 12, 2016, entitled “Quick-Logon for Computing Device,” which is a continuation of U.S. patent application Ser. No. 13/752,211, filed Jan. 28, 2013, now abandoned, which claims priority from U.S. Provisional Application No. 61/591,186, filed Jan. 26, 2012, entitled “Quick-Logon For Personal Computer,” each of which is herein incorporated by reference in their entireties for all purposes.

TECHNICAL FIELD

Various embodiments of the present disclosure generally relate to identity authentication. More specifically, various embodiments of the present application relate to methods and systems for verifying identity on a personal computer using two-factor authentication.

BACKGROUND

The protection and security of customer information is vital from an organization's perspective, not only to comply with applicable laws, but to earn and maintain customer trust. Enhanced security often comes at the cost of convenience for the user, such as by requiring the user to answer additional security questions. Various methods are used in authenticating a user attempting to access an account. Security analysts have identified three authentication factors that can be used in making a positive identification: ownership, knowledge, and inherence. Elements used to verify the first factor, ownership, may include a phone, a security token, or a software token. Elements used to verify the knowledge factor may include a password, username, personal identification number (PIN), or answers to security questions. Elements used to verify the inherence factor may include biometric data.

Verifying two of the factors, “two-factor authentication”, is commonly used to authenticate a user. For example, many applications on mobile devices require the user to enter a PIN, satisfying the knowledge factor, on a particular mobile device, satisfying the ownership factor. In some mobile devices, the ownership factor is generally assumed to be satisfied because many mobile devices, such as smartphones, are particular to one person. Thus, an impersonator would be required not only to have the mobile device, but also to know the PIN in order to access the application. This enables users to simply input a PIN into an application on a mobile device to be authenticated.

Personal computers (computing devices) pose additional complexities in authenticating users. Computing devices are commonly used by more than one person. Thus, it is not safe to assume that the identity of the computing device satisfies the ownership factor. Additionally, computing devices in general have been more easily compromised than other devices. Current solutions increase security, but are often inconvenient for users. For example, one solution includes providing users with some type of token, requiring the user to prove that the user has the token, such as by typing in a one-time code generated by the token in combination with a username/password/PIN. Other solutions focus on the knowledge factor such as by requiring the user to answer additional security questions.

SUMMARY

Disclosed herein are methods and systems for verifying a user's identity on a computing device using two-factor authentication. More particularly, the system can use a personal identification number input by a user, together with one or more of a secure browsing feature, a device fingerprint, and a token generator to authenticate the user on the computer.

When multiple embodiments are disclosed, still other embodiments of the present disclosure will become apparent to those skilled in the art from the following detailed description, which shows and describes illustrative embodiments of the disclosure. As will be realized, the disclosure is capable of modifications in various aspects, all without departing from the scope of the present disclosure. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present disclosure will be described and explained through the use of the accompanying drawings in which:

FIG. 1 illustrates an example of an operating environment in which some embodiments of the present disclosure may be utilized;

FIG. 2 illustrates a method of operation used in accordance with some embodiments of the present disclosure;

FIG. 3 illustrates a method of operation used in accordance with some embodiments of the present disclosure;

FIG. 4 is a flow chart illustrating a set of exemplary operations for registration in accordance with some embodiments of the present disclosure;

FIG. 5 is a flow chart illustrating a set of exemplary operations for using the quick-logon system in accordance with some embodiments of the present disclosure;

FIG. 6 is a block diagram illustrating exemplary components that can be included in a quick-logon system in accordance with various embodiments of the present disclosure;

FIG. 7 is a flow chart illustrating a set of exemplary operations for registration in accordance with some embodiments of the present disclosure;

FIG. 8 is a flow chart illustrating a set of exemplary operations for verifying a user in accordance with some embodiments of the present disclosure;

FIG. 9 is a flow chart illustrating a set of operations for authenticating a user with a secure token; and

FIG. 10 illustrates an example of a computer system with which some embodiments of the present disclosure may be utilized.

The drawings have not necessarily been drawn to scale. For example, the dimensions of some of the elements in the figures may be expanded or reduced to help improve the understanding of the embodiments of the present disclosure. Similarly, some components and/or operations may be separated into different blocks or combined into a single block for the purposes of discussion of some of the embodiments of the present disclosure. Moreover, while the disclosure is amenable to various modifications and alternative forms, specific embodiments have been shown by way of example in the drawings and are described in detail below. The intention, however, is not to limit the disclosure to the particular embodiments described. On the contrary, the disclosure is intended to cover all modifications, equivalents, and alternatives falling within the scope of the disclosure as defined by the appended claims.

DETAILED DESCRIPTION

Various embodiments of the present disclosure generally relate to verifying a user's identify on a computing device (e.g., mobile device, computing device, tablet, etc.) without requiring the user to enter more than one piece of information (e.g., a PIN, password, security question, etc.) More specifically, quick-logon for a computing device of various exemplary embodiments utilizes a PIN input by a user together with a transparent verification of one or more characteristics related to the user and/or the computing device (e.g., one or more of a secure browsing feature, a device fingerprint, a token, a behavioral characteristic, a biometric characteristic, etc.). According to some embodiments, the quick-logon system allows a registered user on a registered computing device to be verified using multiple factor authentication, where the only required user input is a PIN.

In one example, the system allows the user to enter a PIN and then in response to proper entry of the PIN, the system performs a multi-step authentication process by which certain characteristics of the computing device and/or the user are verified in order to achieve a confidence level that the user is who the user claims to be. When the confidence level exceeds a threshold confidence level, the system allows the user access to the system.

For example, in response to correct entry of the PIN, the system may verify that a particular secure browser (e.g., a browser with malware detection and mitigation technology) is installed on the user's device. If such a secure browser is installed on the user's device, the system may allow access or seek to develop a higher level of confidence in the user's identity.

For instance, the system may verify that the device fingerprint matches the device fingerprint that the browser was initially installed upon. If the device fingerprint does not match the device fingerprint of the device upon which the browser was initially installed, the system may determine that access should be denied because it would appear that the browser was moved to a different machine. This may be a sign that an unauthorized user is attempting to circumvent the system by moving the secure browser to another device.

In another example, the system may monitor a user's behavior as reflected by the user's input/output characteristics (e.g., key strokes, mouse movements, browsing behavior, etc.). If the user's behavior matches, within a particular degree of tolerance, the expected behavior within a user profile, the system may determine to allow access because the user's identity is verified. However, if the behavior characteristics do not match the user's profile, the system may deny access because it may appear that the user's PIN and device were hijacked by an unauthorized user.

In another example, the system may transparently monitor a user's biometric characteristics (e.g., fingerprint, voice, retina, etc.) and verify the user's identity through comparing the monitored characteristic(s) to those stored in a user profile.

The preceding examples were provided for exemplary purposes only. It should be understood that any or all of the preceding characteristics could be used to achieve confidence in the user's identity. Moreover, the recited order was provided for exemplary purposes only, and it should be understood that various orders and combinations could be used to verify identity depending on how strict or lax the system administrators wish the security policy to be.

To use the quick-logon system, the user must register on a computing device. Registration allows the organization to gather information and install processes used to verify the user's identity during quick-logon. The registration process involves exchanging communication with the computing device (client) and the organization server, and in some instances, one or both of the computing device and organization server may exchange communication with a third party server. Prior to registration, the user's identity is verified to some threshold.

For example, the user may be required to logon to the system using traditional methods such as providing a username and password, or the user may be required to answer security questions. In many instances, additional data is required, such as a token, a PIN, or answers to a security question. After the user's identity is verified to a certain level, the user must grant permission to install the quick-logon system on the computing device.

The quick-logon installation process involves creating a device fingerprint that identifies the computing device and can be used as an identity indicator for the user. The device fingerprint may be stored on the organization server and associated with the user. Next, the server may provide a client-side executable to install a secure browsing solution on the computing device.

The organization may then request an activation code for a token generator from a third party, which the organization then sends to the computing device. In return for the activation code from the computing device, the third party may provide a serial number and a shared secret key for the token generator.

Next, the organization may associate the token generator with the user using a user identification number, for example. The token generator may then be installed on the computing device. During the registration process, the shared secret key associated with the token generator may be embedded and/or encrypted on the computing device. The token generator is used during quick-logon to generate a one-time code.

In some embodiments, the token generator may be removed after the user terminates a session or after the quick-logon process is complete and re-installed when the user launches quick-logon. Alternatively, it may remain on the computing device. Prior to installation, the user may receive information about what to expect during the installation. Additionally, the user may receive dialogue boxes during installation, informing the user of the progress and activities.

Further, the user may be required to enter additional data that can be used to verify the user's identity. For instance, the user may have to input various biometric data. In another example, the system may transparently monitor the user's behavior (e.g., keystroke patterns, browsing history, etc.) to determine a behavior profile for the user.

In accordance with some embodiments of the disclosure, to use the quick-logon system, the user accesses the organization website. Detecting that the computing device is registered, the user is directed to a PIN input page. After the user inputs their PIN, a number of validations take place before the user is granted access. The validations may include determining that secure browsing is enabled (this may be done prior to quick-logon), verifying the stored device fingerprint with the accessing computing device's device configuration, validating the PIN, and validating the one-time code generated by the token generator. Other validations may take place, as the system is not limited to the aforementioned techniques. Thus, the user may be validated using two-factor authentication on a computing device.

In some scenarios, multiple users access the same computing device. In accordance with some embodiments of the present disclosure, the system provides for multiple user situations by allowing multiple users to register on the same computing device. For users having the same profile or logon to the computing device, each user is provided with a separate token generator requiring a separate shared secret key. In such circumstances, the device fingerprint does not need to be recreated, rather it is associated with the second user, and the secure browser does not need to be re-installed. However, if the users are logged onto the computing device with different profiles, then the multiple users will proceed with a typical installation process as if no other user has been registered on the computing device.

In the following description, embodiments include a token generator as an optional feature in verifying the user's identification. However, the functionality of the token generator may be replaced with or used in addition to a secure or obfuscated key that represents the computer and/or the user. During installation, the organization server may install a secure or obfuscated key or certificate on the computing device. This key would be static, unlike the codes that are generated from the token generator. During quick-logon, the key may be verified by the organization server. The key may be associated on the server side with the user such as with a user identification number. Or the key may be associated with the personal computer. Thus, the key may be per user or per machine. The key may be stored in any manner on the personal computer known to those skilled in the art, such as in a secure key ring.

For additional security during the registration and quick-logon process, during the exchange of information between the personal computer and the organization server, relevant data (i.e., data that will be used in the authentication process) may be combined or padded with irrelevant data. For example, while collecting the personal computer's computer name, the organization server may request several irrelevant files. Additionally, the data may be stored with irrelevant data. Thus, transmitted and stored information may be more secure because potential hackers will be forced to determine the relevant information, resulting in a more secure overall authentication process.

In some embodiments, once the one-time or static code (“secure token”) is generated or installed on the computing device, it is displayed in human-readable form to the user for additional purposes such as for further authentication during an interaction with the user. For example, when the user is accessing a mobile application on a smartphone, the secure token used to authenticate the device can be stored in a tab in the application. If the user calls a representative, the secure token can be provided (e.g., spoken, texted, emailed) to the representative for authentication. Or, the secure token can be provided to the application if the user wants to perform a transaction requiring additional authentication. In some embodiments, the secure token can be provided on a lock screen of the device. In some embodiments, the secure token is a bar code, quick response code, or similar code that can be read by a user's device.

Hence, the methods and systems described provide for a quick-logon experience for the user on a computing device, while preserving, and in many cases enhancing, security. Because the authentication is tied to a particular computing device, embodiments of the present disclosure are best utilized on computing devices that are used multiple times by a user to access accounts, such as a computer used at home or at work.

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, to one skilled in the art that embodiments of the present disclosure may be practiced without some of these specific details.

FIG. 1 illustrates an example of an operating environment 100 in which some embodiments of the present disclosure may be utilized. The embodiments of the present disclosure illustrated in FIG. 1 allow user interaction between user 110 and/or user 120 with computing device 130 (such as a mobile device; a mobile phone; a telephone; a tablet computer; a mobile media device; a mobile gaming device; a vehicle-based computer; a dedicated terminal; a public terminal, desktop, or laptop computer; a kiosk; wearable devices such as a smartwatch; etc.). User 110 and user 120 may be users, customers, or members of the organization utilizing personal computer 130. In some embodiments, in order to register for quick-logon, the user needs administrative access to the computer. Although only two users are shown, more users may utilize computing device 130 in accordance with various embodiments of the disclosure. Computing device 130 can run one or more clients that allow a user to interact with organization server 145 and third party server 150 through network 140. Such clients can be webpages and/or custom applications and may provide access to organization services such as bank processing systems.

As illustrated in FIG. 1, network 140 can be communicably coupled to computing device 130, third party server 150, and organization server 145. Organization server 145, third party server 150 and personal computer 130 may exchange communication via network 140. In some embodiments, communication channels between computing device 130, third party server 150, and organization server 145 are encrypted using any method known in the art. In some examples, the information exchanged is also encrypted using any method known in the art.

Computing device 130 may be any computer connected to network 140. For example, computing device 130 may be a desktop computer, netbook, tablet computer (a portable computer having a touch interface), or an Internet-enabled television device, etc. In some embodiments, computing device 130 may be a mobile device such as a cellular phone, smart phone (a smart phone being a cellular phone that has capabilities and features such as, but not limited to, Internet access, a full keyboard, email access, Wi-Fi connection capabilities, BLUETOOTH connectivity, or any other functionality of a computer), or a laptop computer possibly with a wireless connection (such as an 802.11a/b/g connection or mobile broadband connection, such as via a 3G or 4G wireless network). Personal computer 130 may be shared by co-workers in a work environment such as by deployed navy members on a ship.

Organization server 145 may be the server of an organization that includes one or more membership organizations, banks, credit unions, or other financial institutions. In accordance with embodiments of the present disclosure, organization server 145 can store information regarding users. In some embodiments, organization server 120 stores information including user identification number, membership identification number, phone number, address, etc. Organization server 145 may run various server side applications.

Third party server 150 may be any server that is external to the organization system. One or more third parties having one or more servers may be used to provide specific services, such as security services, to the organization and/or users of the organization. Third party server 150 may store information about users in the organization or services provided to particular users. For example, the third parties may provide secure browsing software, or third parties may provide a token generator, including a shared secret key required to generate the one-time code from the token generator.

In another example, third party server 150 may receive periodic communications from computing device 130 identifying the health of the computing device 130 with respect to certain predetermined criteria. For instance, if malware is detected on computing device 130 through the utilization of secure browsing technology, computing device 130 may notify third party server 150 of such malware detection. Third party server 150 may keep a log of all such malware detections. By keeping track of malware detection instances, third party server 150 shall maintain an understanding of the security health of computing device 130. If the relative health of computing device 130 drops below a predetermined threshold, mitigation measures may be commenced. For instance, third party server 150 may notify organization server 145 that computing device 130 no longer provides a secure environment, and quick-logon will be disabled for computing device 130. It should be noted that if third party server 150 is not utilized, then the preceding functions may be performed by organization server 145 itself.

FIG. 2 illustrates an exemplary method of operation used in accordance with some embodiments of the present disclosure. The method illustrated in FIG. 2 may be used to register a user and computing device for quick-logon. In this example, a third party server 150 is included; however, in various embodiments, additional third parties may be used, or no third party may be used. Furthermore, for purposes of this example, computing device 130 has not been registered for quick-logon by this user or any other user. A user may interact with personal computer 130 to access an organization's website. By virtue of accessing the organization's website, the organization server 145 begins collecting information from computing device 130. The information may include any configuration information about the desktop environment including low level device configuration, hardware identification, clock speed, and the like. The server detects whether any user has registered this computing device; if the computing device has been registered by a user, the user is directed to a quick-logon page. If, however, the computing device has not been registered, the user accesses the logon page of the organization and provides the necessary verification information to logon to the user's account. The verification information may include a username, password, pin, security question, token, grid card, etc. Once the user has been verified to an acceptable level, the user may be presented with the option of registering for quick-logon in connection with the computing device. If the user expresses a desire to register, then the user is presented with a dialogue box or webpage providing information and/or instructions about the registration process. For example, the informational page may tell the user that the certain software will be downloaded to the computing device. The user may also be presented with a page to create a PIN or input an existing PIN.

Additional permission may be requested after the user has an opportunity to read the informational page. If the user grants permission to continue, the quick-logon registration continues with a client-side executable that installs a secure browsing solution on the computing device. After installation, the secure browser ensures that certain activities are observed and that certain features are enabled or disabled during those activities. For example, in an effort to prevent fraud, if a user is logged into a banking website, the secure browser may disable certain recording features such as the snapshot feature. The secure browser may operate every time the browser is used, or only on trusted websites, depending on the type of securing browsing solution used. Different secure browsing solutions provide different abilities. For example, the secure browser may detect malware, disinfect the organization server of any potential threats or weak links in security. The secure browsing solution is generally not user-specific.

During installation, a device fingerprint is created by running software on the computing device or installing an application. The information needed to create the device fingerprint, or the actual device fingerprint, is sent to the organization server and stored. The information recorded when the user initially accessed the organization website may be used. The device fingerprint is associated with the user in the organization server. A newly-created or pre-existing user identification/member identification number may be used to associate the user with the device fingerprint. Although the device fingerprint is not completely unique to the computing device, it can be used as one identity factor when authenticating the user. The device fingerprint provides assurance, at least to a certain threshold, that the system can recognize when portions of the system are compromised and access is attempted from a different computing device.

During installation, a token generator is associated with the user, and a shared secret key associated with the token generator is embedded and installed on the computing device. Each token generator has an activation code, a serial number, and a shared secret key associated with it. In some examples, the organization server requests an activation code for the token generator from a third party. The third party provides the activation code for the token generator to the organization server. The organization server then provides the activation code to the computing device. Upon receiving the activation code, the computing device provides the activation code to the third party and requests the shared secret key and the serial number for the token generator. The third party receives the activation code from the computing device and returns the shared secret key and serial number associated with the token generator to the computing device. The organization server associates the token generator serial number with the user such as by associating the serial number with a user identification number. During the quick-logon process, the shared secret key, in combination with a time stamp, is provided to the token generator upon logon to generate a one-time code. The one-time code is time-sensitive, meaning that the code provided by the token generator is different depending on the time stamp that the token generator is provided. The shared secret key is generally not provided to the organization server. During installation, the shared secret key is encrypted and stored on the computing device. In some embodiments, the shared secret key is encrypted with information including, but not limited to, the user's PIN. At this point, registration is complete, and the user may be granted access to the account. In some embodiments, upon completion of registration or upon logout, the token generator is then removed from the computing device and reinstalled each time the user uses the quick-logon system, providing an extra layer of security. Upon next logon on the computing device, the quick-logon page will be present to the user, and the user will be prompted to provide a PIN to logon.

During registration, dialogue boxes may appear on the computing device to keep the user apprised of the installation process. At completion, the user may be presented with an option to allow for more secure logon when logging on from unregistered devices. For example, the user may be asked if the user prefers additional security such as a token or security questions when logging on from an unregistered computing device or other device. In some embodiments, the user may be provided the option of allowing read-only access when accessing the user's account from unregistered computing devices or if the user is unable to provide the additional security information.

In some embodiments, the organization server 145 detects, during the initial access of the website, that a user has already registered on the computing device. However, the accessing user may be a second user who has not yet registered, as the quick-logon system allows for multiple users to register on the same computing device. As discussed, if the server detects that the computing device is registered, the user is directed to the quick-logon page where the user may enter a PIN. The quick-logon page welcomes back the last quick-logon user and states “Welcome [User Name], please enter your PIN” or something similar. The page may also contain a selection that says, “Not User 110?” (or the like), or a selection such as “Not registered?” (or the like). If the user selects “Not User 110”, a list of other users registered on that computing device may appear, and the user may select appropriately. The user will then be directed to put in the PIN of the user selected. Alternatively, if the user selects the “Not registered” selection, the user is directed to the classic logon page. At this point, the user may logon using the typical methods such as username and password, until the user is verified to an acceptable level. The user may be given the option to register for quick-logon using the methods described. Sometimes, the second user has the same profile as the first user or another user that has registered on the computing device. For example, the first and second users may have the same profile if the users share the same logon name and password to access the computing device. If the first and second users' profiles are the same, the registration process for registering the second user is substantially similar to registering a user on the computing device that no user has registered on. However, the device fingerprint created for the first user already exists, and thus may not be recreated, but rather associated with the additional user. Also, the secure browsing solution will have been previously installed, and thus will not be reinstalled. During installation, dialogue boxes may simply show statuses such as “Device Fingerprint.” A token generator will be assigned for the new user, and a unique shared secret key will be embedded on the computing device for that particular user. Thus, one computing device may have several embedded shared secret keys.

In some examples, the users have different profiles. This may occur if the first user logs onto the computing device under a different username. In this example, the server may not recognize that the first user has registered, and thus the second user is directed to the classic logon page. If the user is verified to the appropriate level and opts to register for quick-logon on the computing device, the installation process may be the same as if no other users have registered on the computing device (secure browsing may be installed, a device fingerprint will be created, and so on).

FIG. 3 illustrates an exemplary method of operation used in accordance with some embodiments of the present disclosure. The method illustrated in FIG. 3 is an example of how quick-logon may operate after installation and during use. The method begins with a request from the computing device to access the organization website. The organization server collects, analyzes, and stores information about the computing device. Detecting that this computing device has been registered for quick-logon, the user is directed to the PIN input page. Assuming the user was the last registered user to use quick-logon on the computing device, the user inputs their PIN, which may be sent to the organization server. If the token generator was previously removed, the computing device downloads the token generator associated with the user from the organization server. Next, the token generator generates a one-time code. The token generator is configured to generate different codes depending upon the time stamp. To generate such a one-time code, the token generator requires the shared secret key that was encrypted and embedded on the computing device during the installation process, in addition to a time stamp. Various pieces of information or data may be used to decrypt the shared secret key. For example, in some embodiments, the user's PIN may be used to decrypt the shared secret key. Once the shared secret key is decrypted, the shared secret key and a time stamp are provided to the token generator. The one-time code and time stamp are sent to the server. The server then validates the user using the various pieces of information. For example, the server may validate the user's PIN, the device configuration, and the one-time code. The server may also perform checks to determine if the secure browser is enabled. In other embodiments, the system may require the secure browser to be enabled prior to allowing the user to logon. To validate the one-time code, the server may match the one-time code with the token generator serial number associated with the user. The one-time code, time stamp, and token generator serial number are sent from the server to the third party where third party validation of the one-time code is requested. Using the time-stamp of the one-time code, and the token generator serial number, the third party server validates the one-time code. If the server verifies the user to a certain level, the user is authenticated and granted access.

The quick-logon system may include additional verifying features that may be used in combination with other features. For example, in addition to the device fingerprint, secure browsing, token generator, a secure or obfuscated key that represents the computer and/or the user may be used.

In some embodiments, the secure token is provided in human-readable form to the user and used for other purposes such as further authentication. The secure token can, for example, be provided on the lock screen of the user's device, in an account profile on a web portal accessible in the user's account, in a tab of a mobile application, or messaged (e.g., texted, emailed, pushed) to the device or a separate device associated with the user. The user may be asked to provide (e.g., speak, text, chat) the secure token to a representative or a device to provide additional authentication. In some embodiments, previous versions of the secure token are stored in the user's profile, on the user's lock screen (e.g., in time order or associated with a date), and a specific one (or more) of the secure tokens is requested. In other embodiments, only the latest secure token is stored in the user's account.

Additional authentication may be requested, for example, when the user wants to contact the entity or an affiliated entity using a different channel than the secure token was generated on. For example, if the secure token was generated or installed on the user's smartphone or desktop and the user contacts a representative (e.g., phone call, chat, or videoconference), then additional or different authentication may be required. Additional authentication may be required if the user requests a transaction or information requiring a certain level of authentication (e.g., the user requests a wire transfer of a significant sum of money). Additional authentication may be required if the user's account shows suspicious activity (e.g., potential fraudulent transactions, the secure browsing feature could not be verified). In some embodiments, the user is asked to read the secure token aloud to the representative or device such that the user's biometrics can be verified as an additional authentication check. In other embodiments, the user can text or email the secure token to the entity for verification. In some embodiments, the secure token can be provided on a lock screen of the device. In other embodiments, the secure token is not provided in human readable form but can be transferred for verification (e.g., a digital certificate, quick response code, bar code).

In some embodiments, when the secure token is a quick response code (or similar type of code, the user can use the secure token to obtain or transfer authentication information to a second client device. In some embodiments, the quick response code can include information in addition to the authentication information, such as transaction information, transaction history, preferences or other information. For example, the user could use the secure token to transfer authentication information and a current or saved transaction from a smartphone to an ATM, kiosk, or other computing device. In another example, the user could receive at a smartphone a quick response code form an ATM, kiosk or other computing device in use by the user. Such a transfer of information, including authentication information and/or transaction information can prevent fraud by extending the security control into the physical realm. That is, to present the quick response code or bar code, the user is required to physically place the device's screen or camera in front of a camera or screen in real time. Additionally, the secure token provides a secure mechanism to transfer information between the two devices. In other embodiments, the secure token could be included in a quick response code.

FIG. 4 is a flow chart illustrating a set of exemplary operations for registration in accordance with some embodiments of the present disclosure. In this embodiment, no user with the same profile has registered on this computing device. As described above, the registration process may be slightly different for a second user if a first user has registered on the computing device using the same profile. In block 410, a user accesses an organization website on a computing device. In block 420, the user logs on to an account at the organization by providing the verifying information such as a username, password, token, PIN, and the like. Once verified to a certain threshold, the user receives an invitation to register for quick-logon, as shown in block 430. In block 440, the user is presented with an information page and asked if the user would like to proceed with quick-logon installation. In block 450, if the user chooses to proceed, quick-logon is installed on the computing device. The user receives status updates as the installation occurs. In block 460, when the installation is complete, the user is presented with various logon options for when the user logs on using a different machine.

FIG. 5 is a flow chart illustrating a set of exemplary operations 500 for using the quick-logon system in accordance with some embodiments of the present disclosure. In block 510, the user accesses the organization website using the registered computing device. Upon detecting that the computing device is registered, the user is directed to the PIN input page. In block 520, the user inputs a PIN. In block 530, after all the checks are performed in the background, the user is verified and granted access.

FIG. 6 is a block diagram illustrating exemplary components that can be included in a quick-logon system in accordance with various embodiments of the present disclosure. According to the embodiments shown in FIG. 6, the quick-logon system 600 can include memory 610, one or more processors 620, registration detection module 630, device fingerprint module 640, token generator module 650, communication module 660, PIN validating module 670, user authentication module 680, and secure browsing module 690. Other embodiments of the present disclosure may include some, all, or none of these modules and components along with other modules, applications, and/or components. Still yet, some embodiments may incorporate two or more of these modules into a single module and/or associate a portion of the functionality of one or more of these modules with a different module.

For example, in one embodiment, the functionality associated with user authentication module 680 and PIN validating module 670 can be incorporated into a single authentication module. As another example, in one embodiment, the token generator module 650 can be separated into a token generator module configured to generator tokens, a token generator installation module configured to install the token generator onto the client, and a token generator module configured to associate the token generator with the user.

Memory 610 can be any device, mechanism, or populated data structure used for storing information. In accordance with some embodiments of the present disclosure, memory 610 can be random access memory, memory storage devices, optical memory devices, media magnetic media, floppy disks, magnetic tapes, hard drives, SIMMs, SDRAM, DIMMs, RDRAM, DDR RAM, SODIMMS, erasable programmable read-only memories (EEPROMs), compact disks, DVDs, and/or the like. In accordance with some embodiments, memory 610 may include one or more disk drives, flash drives, one or more databases, one or more tables, one or more files, local cache memories, processor cache memories, relational databases, flat databases, and/or the like. In addition, those of ordinary skill in the art will appreciate many additional devices and techniques for storing information which can be used as memory 610.

Memory 610 may be used to store instructions for running one or more applications or modules on processor(s) 620. For example, memory 610 could be used in one or more embodiments to house all or some of the instructions needed to execute the functionality of registration detection module 630, device fingerprint module 640, token generator module 650, communication module 660, PIN validating module 670, user authentication module 680, and secure browsing module 690.

FIGS. 7-9 are flowcharts illustrating various sets of operations. In some embodiments, fewer than all of the operations in each set of operations are performed, whereas in other embodiments, additional operations are performed. Moreover, in some embodiments, the operations may be performed in different orders or in parallel. The operations can be performed by various components and systems such as those illustrated in FIG. 1 and FIG. 6.

FIG. 7 is a flow chart illustrating a set of operations 700 for registration in accordance with some embodiments of the present disclosure. Receiving operation 710 receives a request from a device to view a website. Collecting operation 720 collects and records information from the requesting device. Determining operation 730 determines that the device and user are not registered for quick-logon. Receiving operation 740 receives user instruction to proceed with quick-logon enrollment. Installing operation 750 installs a secure browser. Creating operation 760 creates a device fingerprint. Embedding operation 770 embeds and encrypts a token generator and shared secret key.

FIG. 8 is a flow chart illustrating a set of operations 800 for verifying a user in accordance with some embodiments of the present disclosure. Verifying operation 810 verifies that the secure browsing feature is enabled. Verifying operation 820 verifies the user's PIN. Verifying operation 830 verifies the one-time code. Verifying operation 840 verifies the device configuration. Granting operation 850 grants the user access to the account.

FIG. 9 is a flow chart illustrating a set of operations 900 for authenticating a user with a secure token. Receiving operation 910 receives a secure token from a computing device. The secure token can be used to fulfill a first authentication request. The secure token can be provided without instruction from the user, meaning that the secure token is made available by the computing device without the user providing the secure token. In some embodiments, the user may first provide authentication such as a PIN or other identifier, prior to the computing device providing the secure token, but again, the user does not type in or otherwise provide the secure token. Verifying operation 920 verifies that the secure token matches the secure token stored in the user profile.

Authenticating operation 930 authenticates the user to engage in a first activity on a first channel without further interaction from the user in response to verification that the secure token matches the secure token stored in the user profile. For example, the user may be allowed to check the user's bank account (activity) via a mobile application (channel) after the secure token is verified. Other examples of activities include transferring funds, setting up an account, and purchasing a product or service. Examples of channels include mobile applications, web portals, voice and data phone calls, voice only calls, chat rooms, email, and text messages. Providing operation 940 gives the user access to the secure token. That is, the secure token can be, for example, displayed on a lock screen of the device, sent to the user via email, stored on a page of a mobile application or a website portal accessible to the user, or messaged via push notification or text message to a device of the user. The secure token can be dynamically generated such as using the token generator or the secure token can be static. If the secure token is dynamic, the secure token and previously provided secure tokens can be provided to the user with time stamps.

Receiving request 950 receives a request for a user to engage in an activity or channel that requires additional authentication. The activity can be a different activity on the same channel that requires additional authentication. For example, if the channel is a mobile application, the first activity is checking a bank account, and the second activity is wiring a large sum of money to another account, additional authentication may be required. In another example, the user could perform the same activity on a second channel which can require additional authentication. For example, if the first channel is a mobile application, the second channel is a voice-only phone call, and the activity is checking a balance on a bank account, the user may be required to provide additional authentication due to the change in channels.

Requesting operation 960 requests a secure token from the user to provide the additional authentication. The user can provide the secure token in various ways. For example, the user can send the secure token via email, text message, chat message, or read aloud the token via a phone or video call. In some embodiments, the secure token is in a human-readable form such that the user can read aloud the secure token. In such cases, the user's biometrics can be verified as well. For example, the user's voice biometrics can be verified by comparing a biometric characteristic of the user speaking the secure token with a stored biometric characteristic of the user in the user profile and verifying the identity of the user when the biometric characteristic of the user speaking the secure token matches the stored biometric characteristic.

Authenticating operation 970 authenticates the user to the second activity or to the second channel after verifying that the secure token provided by the user matches a stored secure token. In some embodiments, additional credentials are checked such as biometrics, browsing history, and expected behavior.

FIG. 10 illustrates an example of a computer system with which some embodiments of the present disclosure may be used.

Computer System Overview

Embodiments of the present disclosure include various steps and operations, which have been described above. A variety of these steps and operations may be performed by hardware components or may be embodied in machine-executable instructions, which may be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps. Alternatively, the steps may be performed by a combination of hardware, software, and/or firmware. As such, FIG. 10 is an example of a computer system 1000 with which embodiments of the present disclosure may be utilized. According to the present example, the computer system 1000 includes an interconnect 1010, at least one processor 1020, at least one communication port 1030, a main memory 1040, a removable storage media 1050, a read-only memory 1060, and a mass storage device 1070.

Processor(s) 1020 can be any known processor, such as, but not limited to, Intel® Itanium® or Itanium 2® processor(s), or AMD® Opteron® or Athlon MP® processor(s), or Motorola® lines of processors. Communication port(s) 1030 can be an RS-232 port for use with a modem-based dial-up connection, a 10/100 Ethernet port, or a Gigabit port using copper or fiber. Communication port(s) 1030 may be chosen depending on the type of network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 1000 connects.

Main memory 1040 can be RAM or any other dynamic storage device(s) commonly known in the art. Read-only memory 1060 can be any static storage device(s) such as programmable read-only memory (PROM) chips for storing static information, such as instructions for processor(s) 1020.

Mass storage device 1070 can be used to store information and instructions. Mass storage devices that may be used include hard disks such as the Adaptec® family of small computer system interface (SCSI) drives, optical discs, or an array of discs such as redundant array of independent disks (RAID), the Adaptec® family of RAID drives, or any other mass storage device.

Interconnect 1010 communicatively couples processor(s) 1020 with the other memory, storage, and communication blocks. Depending on the storage devices used, interconnect 1010 can be a PCI/PCI-X- or SCSI-based system bus.

Removable storage media 1050 can be any type of external hard drive, floppy drive, IOMEGA® Zip Drives, CD-ROM, compact disc re-writable (CD-RW), and/or digital video disc read-only memory (DVD-ROM).

The components described above are meant to exemplify some types of possibilities. In no way should the aforementioned examples limit the disclosure, as they are only exemplary embodiments.

Terminology

Brief definitions of terms, abbreviations, and phrases used throughout this application and the appendices are given below.

The terms “connected” or “coupled” and related terms are used in an operational sense and are not necessarily limited to a direct physical connection or coupling. Thus, for example, two devices may be coupled directly or via one or more intermediary media or devices. As another example, devices may be coupled in such a way that information can be passed therebetween, while not sharing any physical connection with one another. Based on the disclosure provided herein, one of ordinary skill in the art will appreciate a variety of ways in which a connection or a coupling exists in accordance with the aforementioned definition.

The phrases “in some embodiments,” “according to some embodiments,” “in the embodiments shown,” “in other embodiments,” “embodiments,” and the like, generally mean that the particular feature, structure, or characteristic following the phrase is included in at least one embodiment of the present disclosure and may be included in more than one embodiment of the present disclosure. In addition, such phrases do not necessarily refer to the same embodiments or to different embodiments.

If the specification states a component or feature “may,” “can,” “could,” or “might” be included or have a characteristic, that particular component or feature is not required to be included or have the characteristic.

The term “responsive” encompasses being completely or partially responsive.

The term “module” refers broadly to a software, hardware, or firmware (or any combination thereof) component. Modules are typically functional components that can generate useful data or other output using specified input(s). A module may or may not be self-contained. An application program (also called an “application”) may include one or more modules, or a module can include one or more application programs.

The term “network” generally refers to a group of interconnected devices capable of exchanging information. A network may be as small as several personal computers on a LAN or as large as the Internet, a worldwide network of computers. As used herein, “network” is intended to encompass any network capable of transmitting information from one entity to another. In some cases, a network may comprise multiple networks—even multiple heterogeneous networks—such as one or more border networks, voice networks, broadband networks, financial networks, service provider networks, Internet service provider (ISP) networks, and/or public switched telephone networks (PSTNs) interconnected via gateways operable to facilitate communications between and among the various networks.

Also, for the sake of illustration, various embodiments of the present disclosure have herein been described in the context of computer programs, physical components, and logical interactions within modern computer networks. More importantly, while these embodiments describe various embodiments of the present disclosure in relation to modern computer networks and programs, the method and apparatus described herein are equally applicable to other systems, devices, and networks, as one skilled in the art will appreciate. As such, the illustrated applications of the embodiments of the present disclosure are not meant to be limiting, but instead are meant to be examples. Other systems, devices, and networks to which embodiments of the present disclosure are applicable include, but are not limited to, other types of communication and computer devices and systems. More specifically, embodiments are applicable to communication systems, services, and devices, such as cell phone networks and compatible devices. In addition, embodiments are applicable to all levels of computing, from the personal computer to large network mainframes and servers.

In conclusion, the present disclosure discloses novel systems, methods, and arrangements for quick-logon to a computing device. While detailed descriptions of one or more embodiments of the disclosure have been given above, various alternatives, modifications, and equivalents will be apparent to those skilled in the art without varying from the spirit of the disclosure. For example, while the embodiments described above refer to particular features, the scope of this disclosure also includes embodiments that have different combinations of features, and embodiments that do not include all of the described features. Accordingly, the scope of the present disclosure is intended to embrace all such alternatives, modifications, and variations that fall within the scope of the claims, together with all equivalents thereof. Therefore, the above description should not be taken as limiting. 

What is claimed is:
 1. A computer-implemented method comprising: sending, from a computing device associated with a user to a server, a secure token to fulfill a first authentication request, wherein the secure token is generated by a token generator associated with the computing device, wherein the user is permitted to engage in a first activity after authentication, wherein authentication includes at least verification that the secure token matches a secure token generated by the token generator associated with the computing device; receiving, from the server, access to the secure token in a human-readable format to fulfill a second authentication request associated with a second activity having a different level of authentication than the first activity; requesting engagement in the second activity; and sending, to the server, the secure token, wherein the secure token is the same secure token that was used to fulfill the first authentication request, wherein the user is permitted to engage in the second activity upon verification that the secure token matches the secure token generated by the token generator associated with the computing device.
 2. The method of claim 1, wherein receiving, from the server, access to the secure token comprises at least one of: displaying the secure token on a lock screen of the computing device or storing the secure token in an application installed on the computing device.
 3. The method of claim 1, wherein the second activity requires a higher level of authentication than the first activity.
 4. The method of claim 1, wherein the secure token is dynamic, wherein the first activity takes place via a first channel, wherein the first channel is one of: a mobile application, a web portal, a chat room, a voice and data call, or a voice call.
 5. The method of claim 4, wherein the second activity takes place via a second channel, wherein the second channel is different than the first channel.
 6. The method of claim 1, wherein the secure token is a quick response code, wherein the quick response code is physically presented to a second device.
 7. The method of claim 1, wherein authenticating the user comprises verifying an identity of the user, wherein verifying the identity of the user further includes: monitoring interactions of the user including browsing behavior with the computing device; determining whether the interactions of the user with the computing device matches, within a predetermined degree of tolerance, expected behavior within a user profile of the user; and in response to the interactions of the user matching the expected behavior within the user profile, verifying the identity of the user.
 8. A non-transitory computer-readable medium comprising instructions stored thereon, that when executed on a processor, perform operations comprising: sending, from a computing device associated with a user to a server, a secure token to fulfill a first authentication request, wherein the secure token is generated by a token generator associated with the computing device, wherein the user is permitted to engage in a first activity after authentication, wherein authentication includes at least verification that the secure token matches a secure token generated by the token generator associated with the computing device; receiving, from the server, access to the secure token in a human-readable format to fulfill a second authentication request associated with a second activity having a different level of authentication than the first activity; requesting engagement in the second activity; and sending, to the server, the secure token, wherein the secure token is the same secure token that was used to fulfill the first authentication request, wherein the user is permitted to engage in the second activity upon verification that the secure token matches the secure token generated by the token generator associated with the computing device.
 9. The non-transitory computer-readable medium of claim 8, wherein receiving, from the server, access to the secure token comprises at least one of: displaying the secure token on a lock screen of the computing device or storing the secure token in an application installed on the computing device.
 10. The non-transitory computer-readable medium of claim 8, wherein the second activity requires a higher level of authentication than the first activity.
 11. The non-transitory computer-readable medium of claim 8, wherein the secure token is dynamic, wherein the first activity takes place via a first channel, wherein the first channel is one of: a mobile application, a web portal, a chat room, a voice and data call, or a voice call.
 12. The non-transitory computer-readable medium of claim 11, wherein the second activity takes place via a second channel, wherein the second channel is different than the first channel.
 13. The non-transitory computer-readable medium of claim 8, wherein the secure token is a quick response code, wherein the quick response code is physically presented to a second device.
 14. The non-transitory computer-readable medium of claim 8, wherein authenticating the user comprises verifying an identity of the user, wherein verifying the identity of the user further includes: monitoring interactions of the user including browsing behavior with the computing device; determining whether the interactions of the user with the computing device matches, within a predetermined degree of tolerance, expected behavior within a user profile of the user; and in response to the interactions of the user matching the expected behavior within the user profile, verifying the identity of the user.
 15. A call routing system comprising: one or more processors; and a computer readable storage medium having instructions stored thereon, which when executed by the one or more processors, cause the call routing system to: send, from a computing device associated with a user to a server, a secure token to fulfill a first authentication request, wherein the secure token is generated by a token generator associated with the computing device, wherein the user is permitted to engage in a first activity after authentication, wherein authentication includes at least verification that the secure token matches a secure token generated by the token generator associated with the computing device; receive, from the server, access to the secure token in a human-readable format to fulfill a second authentication request associated with a second activity having a different level of authentication than the first activity; request engagement in the second activity; and send, to the server, the secure token, wherein the secure token is the same secure token that was used to fulfill the first authentication request, wherein the user is permitted to engage in the second activity upon verification that the secure token matches the secure token generated by the token generator associated with the computing device.
 16. The call routing system of claim 15, wherein receiving, from the server, access to the secure token comprises at least one of: displaying the secure token on a lock screen of the computing device or storing the secure token in an application installed on the computing device.
 17. The call routing system of claim 15, wherein the second activity requires a higher level of authentication than the first activity.
 18. The call routing system of claim 15, wherein the secure token is dynamic, wherein the first activity takes place via a first channel, wherein the first channel is one of: a mobile application, a web portal, a chat room, a voice and data call, or a voice call, wherein the second activity takes place via a second channel, wherein the second channel is different than the first channel.
 19. The call routing system of claim 15, wherein the secure token is a quick response code, wherein the quick response code is physically presented to a second device.
 20. The call routing system of claim 15, wherein authenticating the user comprises verifying an identity of the user, wherein verifying the identity of the user further includes: monitoring interactions of the user including browsing behavior with the computing device; determining whether the interactions of the user with the computing device matches, within a predetermined degree of tolerance, expected behavior within a user profile of the user; and in response to the interactions of the user matching the expected behavior within the user profile, verifying the identity of the user. 